# Update an existing group rule

Modifies an existing rule's text, hint, or ordering. Requires GroupSettings.Manage permission. The entire rule content must be provided in the update request. Changes are tracked in the audit log for compliance and moderation purposes. Returns 404 if the rule doesn't exist.

RBAC: requires GroupSettings.Manage

Endpoint: PUT /api/v1/groups/{groupId}/rules/{ruleId}
Version: 1.0
Security: header

## Path parameters:

  - `groupId` (string, required)
    The unique identifier of the group containing the rule
    Example: "us_01hxcvk1hjexere4pvtrj0ymqq"

  - `ruleId` (string, required)
    The unique identifier of the rule to update
    Example: "us_01hxcvk1hjexere4pvtrj0ymqq"

## Request fields (application/json):

  - `text` (string, required)
    The rule text that defines expected behavior or policy (max 500 characters)
    Example: "Be respectful to all members"

  - `hint` (string, required)
    Additional context or clarification for the rule (max 500 characters)
    Example: "This includes no harassment, personal attacks, or discriminatory language"

  - `ordering` (integer, required)
    Display order position - rules with lower values appear first
    Example: 1000

## Response 200 fields (application/json):

  - `text` (string, required)
    The rule text that defines expected behavior or policy (max 500 characters)
    Example: "Be respectful to all members"

  - `hint` (string, required)
    Additional context or clarification for the rule (max 500 characters)
    Example: "This includes no harassment, personal attacks, or discriminatory language"

  - `ordering` (integer, required)
    Display order position - rules with lower values appear first
    Example: 1000

  - `id` (string, required)
    Unique identifier for the rule
    Example: "us_01hxcvk1hjexere4pvtrj0ymqq"

## Response 400 fields (application/json):

  - `errorCode` (string, required)
    Error code

  - `message` (string, required)
    Error message

  - `docUrl` (string)
    Link to documentation

## Response 401 fields (application/json):

  - `errorCode` (string, required)
    Error code

  - `message` (string, required)
    Error message

  - `docUrl` (string)
    Link to documentation

## Response 403 fields (application/json):

  - `errorCode` (string, required)
    Error code

  - `message` (string, required)
    Error message

  - `docUrl` (string)
    Link to documentation

## Response 404 fields (application/json):

  - `errorCode` (string, required)
    Error code

  - `message` (string, required)
    Error message

  - `docUrl` (string)
    Link to documentation


